@YFZdude you rock, thank you!

@mitu
I did as told, emulationstation auto config was disabled. I enabled it and also removed xboxdrv.
And it finally works! I could configure both controller, the configuration is kept in the game and even when rebooting I don't need to re-configure it again.

Thanks a lot, the auto config settings were an eye-opener!

@dankcushions Alright thank you already! I do know it's possible to wire it like that but im more worried to how some games will respond to it when trying to play solo. I guess I will keep it simple for my first build and just use 2 separate ones.

EmulationStation uses libSDL's joystick subsystem to recognize and work with joystick devices, maybe your device is not detected by libSDL as a gamepad/joystick.
In addition to jstest/evtest, install jstest-sdl2 (from https://github.com/Grumbel/sdl-jstest) and see if your device is working with it.

@19whity81

Regarding the button configuration, will I need to configure the buttons for each single game or each single emulator or this is just a onetime configuration and it will work for all?

are you following our documentation? this point is covered here: https://retropie.org.uk/docs/First-Installation/#configure-controllers

@grand_national you need to show a screenshot.

service menu is entered pressing F2: https://retropie.org.uk/docs/lr-mame2003/#service-menu

mame menu is entered pressing TAB or R2: https://retropie.org.uk/docs/lr-mame2003/#mame-menu

I guessed at the button config for the controller when EM first started and config'd what I thought to be the minimum.

does not inspire confidence... what layout did you use?

@riverstorm said in MAME 2003 PLUS not letting me use Joystick:

456 123

From mame2003+ official documentation :
The recommended 6-buttons layout for mame2003+ should be this one :
this one
With device type set to 6-Button in Quick Menu > Controls

It should also match the layout FBNeo is expecting by default (when device type is set to Classic)

@jigidyjim

Well, this looks a little disheartening. I can't believe you would have to hardwire a shift/alt button, but I'm glad I found this thread before I went down the rabbit hole. I'm currently using a controller called the iPac and it has a mode that acts like a keyboard as well as a mode where it acts as a USB controller. There is a keymap/button configuration tool and also provides a macro setting. I'm hoping this will be the solution because I don't like the idea of getting into a situation in the future where I have hard-wired macros and the software changes the way it works. Regardless, thanks for the thread which really shortened my research time.

@sth3204 3rd party images are not supported in this forum.
You could either ask the seller of your bartop or install the official image from this site to get help.

@studev That depends on what you want so save:

In Quick Menu > Overrides, you can save custom configurations (overrides) for cores and games, whereas in Quick Menu > Controls you can save custom controller mappings (remap files) for cores and games.

I just checked and there is no under voltage notification.

@neutrios

I have a DragonRise Inc. USB Encoder and haven't had any issues mapping the buttons in Retropie 4.6 on a Raspberry Pi 4 4GB

the config is here ...

/opt/retropie/configs/all/retroarch/autoconfig/DragonRise Inc. Generic USB Joystick .cfg

and inside the .cfg is my button mapping

input_device = "DragonRise Inc. Generic USB Joystick "
input_driver = "udev"
input_enable_hotkey_btn = "6"
input_l_btn = "0"
input_load_state_btn = "0"
input_up_btn = "10"
input_left_btn = "11"
input_state_slot_decrease_btn = "11"
input_select_btn = "6"
input_right_btn = "9"
input_state_slot_increase_btn = "9"
input_r_btn = "5"
input_save_state_btn = "5"
input_y_btn = "4"
input_x_btn = "3"
input_menu_toggle_btn = "3"
input_down_btn = "8"
input_start_btn = "7"
input_exit_emulator_btn = "7"
input_b_btn = "1"
input_reset_btn = "1"
input_a_btn = "2"

More info-

I've confirmed holding the buttons down works in general. I played GIJoe and got the auto-fire and just held the button to get it to continually fire. So it works in theory and works on my cabinet.

Could it be specific in some way to MK2 - nvram, cfg or DIP switch settings?

I'm also not insane, right? Holding block in MK2 should keep the character's block held?

@FormulaFox Good deal.

The documentation for that thing was quite an interesting read.

@johnes You can map then using the Mame internal OSD menu (pressing TAB) to MAME emulator actions, but not to RA's hotkeys.

@orangewaffle

Ok, reaching home, i got the information needed:

Pi Model or other hardware: (B, B+, 2 B, 3, X86 PC etc..) 3 Model B+
Power Supply used: (If using a Pi) Samsung genuine adapter, 2A
RetroPie Version Used (eg 3.6, 3.8.1, 4.1 - do not write latest): 4.3
Built From: (Pre made SD Image on RetroPie website, Berryboot, or on top of existing OS etc.. - please provide the filename of any image used) Pre made SD Image on RetroPie website, but i can't remember which one
USB Devices connected: 2
Controller used: DragonRise Inc. Generic USB Joystick
Error messages received: -
Log found in /dev/shm/runcommand.log (if relevant): -
Guide used: (Mention if you followed a guide)
File: (File with issue - with FULL path): -
Emulator: (Name of emulator - if applicable): can't say, because i can't get into emulator options (nothing happens if i press any button during game load)
Attachment of config files:

After replacing a 1A charger with a 2A one and giving the setup a one day rest, 7 out of 9 buttons work now, instead of 1. Top left button still does nothing, as well as the hotkey button.

In the weekend i will try a clean install of the latest retropie image and keep this post updated.

I think i found it , i didn't connect the buttons at the same place on each PCB !

I may have broken this myself in the beginning when i was messing around alot with RetroArch and the controllers.